You might receive an error or the software might reference the wrong table when you use the ACCESS procedure to create an Access view in SAS/ACCESS Interface to DB2. These potential problems occur when you are running the third maintenance release for SAS 9.2 (TS2M3) under z/OS.

These issues might occur when you set the subsystem with the DB2SSID= system option rather than using the SSID= statement in PROC ACCESS. PROC ACCESS ignores the DB2SSID= system option and uses, instead, the default DB2 subsystem.

If no subsystem named DB2 exists, the following error may occur:

ERROR: (ACCDB2M031E) Cannot connect to DB2 subsystem DB2, rc = 12, reason 
code = 00F30006. Refer to the DB2 documentation for further details. 

If a subsystem named DB2 does exist, the Access view is based on a table in that subsystem rather than the subsystem that is set by the DB2SSID= system option.

Another error that has been seen is

ERROR: DATABASE ERROR. EXAMINE FIELDS AND/OR MESSAGES BELOW

If the second error occurs, turn on tracing with the following options statement:

OPTIONS SASTRACE=',,d,d'; 

and rerun the code. Take a look at the resulting SAS log. If you see the following statement, you are hitting this issue:

DB2: (1) Exiting db2m_conn() with return code -2147483648

The only workaround is to specify the subsystem with a SSID= statement in the PROC ACCESS code.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Applying this hot fix requires you to perform a DB2 bind with new database request module (DBRM) members. Even if you have completed the bind for the third maintenance release for SAS 9.2 (TS2M3) previously, you must perform the bind again with these new DBRM members. For more details, see SAS Note 39564, "SAS® 9.2 (TS2M3) Database Request Module (DBRM) members that are needed for the DB2 bind are not downloaded during the installation".

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to DB2 9.21_M2 is available at: